fix: improve YAML configuration handling and normalize exports - #228
Open
KingIronMan2011 wants to merge 1 commit into
Open
fix: improve YAML configuration handling and normalize exports#228KingIronMan2011 wants to merge 1 commit into
KingIronMan2011 wants to merge 1 commit into
Conversation
KingIronMan2011
marked this pull request as ready for review
July 29, 2026 18:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
conf.ymlfiles to UTF-8 without a BOMRoot cause
Legacy stored configuration could cause the YAML parser to emit malformed shell assignments. The install and remove flows evaluated that output directly, resulting in errors such as
=: command not found. Extension configuration saved with a UTF-8 BOM or UTF-16 encoding could also fail parsing after export.Changes
Stored configuration parsing now accepts only the expected generated variable assignments and warns when malformed entries are ignored. Exported extension configuration is normalized through a Node helper before it is packaged, removing UTF-8 BOMs and converting BOM-marked UTF-16 files to UTF-8.
Validation